Urgent help.  linked mailbox attribute
Hi all, We have Exchange 2007 SP1 and now, most users have linked mailboxes due to merge. So, where does the attribute for linked mailbox hold? in AD or Exchange database? We are going to use Dial Tone portability in case of disaster. If we have linked mailboxes, can we still use dial tone recovery? Thank you.
February 7th, 2011 10:57am

Hi, Why you are keeping mailbox as linked mailbox after migration, you must convert it into user mailbox then you can use it as normal mailbox restore. Please have a look of below article for conversion : http://telnetport25.wordpress.com/2008/06/10/linked-mailbox-conversion-after-migration-in-exchange-2007/Anil
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2011 11:20am

It is the msExchRecipientTypeDetails attribute as Anil referenced. Unless you want to disconnect and reconnect their mailboxes, just update that attribute. All my mailboxes that I migrated cross forest came over as linked with no root cause, no orphaned security descriptors etc. I just had to resort to updating the attribute.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
February 7th, 2011 11:26am

Thank you and so, msExchRecipientTypeDetails attribute is in the AD. After migration, we kept users as linked mailboxes and stay that way too. the question is that if we create the empty dial tone database and run move-mailbox--configurationonly and activate the dial tone database, will users in the dialtone database on the alternate server still stay as linked mailboxes? Thank you for your help.
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2011 12:51pm

Not sure, I'm assuming the configurationonly switch only updates the attributes below and keeps the other exchange attributes in tact. You will have to test unless someone else knows. msExchHomeServerName homeMDB homeMTA James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
February 7th, 2011 2:11pm

Can anyone share if you have such a experience? Thank you.
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2011 5:36pm

Can I use ADSI to change the above attributes to test one user? Thank you.
February 10th, 2011 5:11pm

Yes that's how it's typically done.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
February 10th, 2011 5:18pm

Hi SGryzbowski, Sure, you could make some tests, and in my opinion, it could be test easily. per my known, the linked mailbox in the resources exchange forest, if we do some backup, and we could do the recovery for it, the linked mailbox is some mailbox which account is disabled in the resources server, and then we could linked it any account forest that we want. Regards! GavinPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
February 11th, 2011 2:15am

Still, most users have linked mailboxes due to merge. the question is that if we create the empty dial tone database and run move-mailbox--configurationonly and activate the dial tone database, will users in the dialtone database on the alternate server still stay as linked mailboxes? Thank you for your help.
Free Windows Admin Tool Kit Click here and download it now
February 11th, 2011 9:18am

Hi SGryzbowski, In my opinion, if we move the linked mailbox to other database, it will still be a linked mailbox. If I misunderstand your issue, please tell me. Regards! GavinPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
February 14th, 2011 6:03am

Hmm your last post got removed. You replied that the mailbox remained linked after you restored to dial tone DB, but OWA was not working. Try this set-mailbox -database (point it to the existing DB that the mailbox resides in)James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2011 5:36pm

Hi Gavin, Thank you and it stays a linked mailbox after I run *Get-Mailbox -Database EX1\SG2\MDB2 | Move-Mailbox -ConfigurationOnly -TargetDatabase EX2\<Storage_Group_Name>\MDB2 Can I access the OWA on the EX2 after the above command? I run https://ex2/owa and after login and I got this error: _________________- Outlook Web Access could not connect to Microsoft Exchange. If the problem continues, contact technical support for your organization.\ Request Url: https://EX2:443/owa/default.aspx User host address: 192.168.1.128 Exception Exception type: Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException Exception message: Cannot open mailbox /o=EXCH/ou=exchange administrative group (fydibohf23spdlt)/cn=recipients/cn=test1. Call stack Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString, Boolean secondTry) Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString, Boolean secondTry) Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString) Microsoft.Exchange.Data.Storage.MailboxSession.Initialize(LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags) Microsoft.Exchange.Data.Storage.MailboxSession.CreateMailboxSession(LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags, CultureInfo cultureInfo, String clientInfoString) Microsoft.Exchange.Data.Storage.MailboxSession.Open(ExchangePrincipal mailboxOwner, WindowsPrincipal authenticatedUser, CultureInfo cultureInfo, String clientInfoString) Microsoft.Exchange.Clients.Owa.Core.OwaWindowsIdentity.CreateMailboxSession(ExchangePrincipal exchangePrincipal, CultureInfo cultureInfo) Microsoft.Exchange.Clients.Owa.Core.UserContext.Load(OwaContext owaContext) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.CreateUserContext(OwaContext owaContext, UserContextKey userContextKey, UserContext& userContext) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext) System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) Inner Exception Exception type: Microsoft.Mapi.MapiExceptionLogonFailed Exception message: MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=-2147221231) Diagnostic context: ...... Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 1404 Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2011-02-14 22:18:31:609 Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 2 Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 1722 Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 390 Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 2 Lid: 8856 dwParam: 0x6BA Msg: EEInfo: prm[0]: Unicode string: EX2.mycompany.local Lid: 8856 dwParam: 0x6BA Msg: EEInfo: prm[1]: Unicode string: EX2 Lid: 23065 EcDoConnectEx called [length=69] Lid: 17913 EcDoConnectEx returned [ec=0x80040111][length=56][latency=15] Lid: 19778 Lid: 27970 StoreEc: 0x80040111 Lid: 17730 Lid: 25922 StoreEc: 0x80040111 Call stack Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Int32 ec, DiagnosticContext diagCtx) Microsoft.Mapi.ExRpcConnection.Create(ConnectionCache connectionCache, ExRpcConnectionCreateFlag createFlags, ConnectFlag connectFlags, String serverDn, String userDn, String user, String domain, String password, String httpProxyServerName, Int32 ulConMod, Int32 lcidString, Int32 lcidSort, Int32 cpid, Int32 cReconnectIntervalInMins, Int32 cbRpcBufferSize, Int32 cbAuxBufferSize) Microsoft.Mapi.ConnectionCache.OpenMapiStore(String mailboxDn, Guid mailboxGuid, Guid mdbGuid, ClientIdentityInfo clientIdentity, String userDnAs, OpenStoreFlag openStoreFlags, CultureInfo cultureInfo, String applicationId) Microsoft.Mapi.ConnectionCache.OpenMailbox(String mailboxDn, Guid mailboxGuid, Guid mdbGuid, WindowsIdentity windowsIdentityAs, String userDnAs, OpenStoreFlag openStoreFlags, CultureInfo cultureInfo, String applicationId) Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString, Boolean secondTry) _____________ What other steps I missed? Thank you.
February 14th, 2011 5:39pm

Hmm your last post got removed. You replied that the mailbox remained linked after you restored to dial tone DB, but OWA was not working. Try this set-mailbox -database (point it to the existing DB that the mailbox resides in) James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2011 5:48pm

It that doesn't work, restart the IS store, the store is likley caching stale homemdb attribute.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
February 14th, 2011 5:49pm

Hi James, OWA worked now on the alternate server EX2 with dial done DB and thank you. I did some tests and use Get-Mailbox –Database "EX2\SG2\MDB2" | Export-Mailbox –PSTFolderPath C:\PSTFiles to export pst files and I got pst files. Now, I ran Get-Mailbox -Database EX2\SG2\MDB2 | Move-Mailbox -ConfigurationOnly -TargetDatabase EX1\SG2\MDB2 to move to the original server EX1 Now, I tried to merge the new content on the alternate server EX2 to the server EX1. I ran Get-Mailbox –Database "EX1\SG2\MDB2" | Import-Mailbox –PSTFolderPath C:\PSTFiles1 Then I can not import pst files and the error is [2/15/2011 3:28:24 PM] [0] [test1_admt] Opening PST file. [2/15/2011 3:28:24 PM] [0] [test1_admt] Moving messages. [2/15/2011 3:28:24 PM] [0] [test1_admt] Merging messages. [2/15/2011 3:28:24 PM] [0] [ERROR] Error was found for TestUser (testuser@mycompany.com) because: Error occurred in the step: Moving messages. Failed to copy messages to the destination mailbox store with error: MAPI or an unspecified service provider. ID no: 00000000-0000-00000000, error code: -1056749164 ______________ What might I miss? Thank you.
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2011 4:05pm

Do you have full mailbox rights to the destination mailbox? Error -1056749164 Occurs When You Run the Export-Mailbox Cmdlet on Exchange 2007 SP1 http://technet.microsoft.com/en-us/library/dd285510(EXCHG.80).aspxJames Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
February 15th, 2011 7:31pm

Hi SGyzbowski, James gave some good suggestion, any update for your issue? Regards! GavinPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2011 9:02pm

Here are some updates: I checked and no full mailbox rights. After I assigned the rights and it worked. THANK YOU!!! Actually, when I export and got this error and I did not pay attention too. The EX1 server is the production MBX server and EX2 is the dial tone MBX server. the one user has full mailbox rights on the EX1 server, when I ran -configurationonly to move test users to the server Ex2, the full mailbox rights are not there on the server EX2. So, the full mailbox permission stays on the DB, not AD? Before I ran export-mailbox, I need to assign the user to have full mailbox rights to all mailboxes on the server EX2. How should I assign the full mailbox permission on the server EX2? Can I add this user who needs full rights to the Exchange Domain Servers? Thank you for your help.
February 16th, 2011 11:58am

Correct mailbox rights is an Exchange permission. However if you granted the receive-as rights on the DB the access would've preserved. This example grants the user Ayla Kol Receive As permission for mailboxes on mailbox database DB01. Ayla will be able to log on to every mailbox on that database. Add-ADPermission -Identity "DB01" -User "Ayla" -ExtendedRights Receive-As James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2011 12:04pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics